-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid cascade cycles on SQL Server for derived-type referencing many-to-many #28937
Conversation
@AndriySvyryd I just realized that maybe we should only do this when both types are mapped to the same table? So, for TPH? Or would it be a cycle anyway? |
Yes, just TPH |
In fact, the check should only be about the tables, not inheritance, as both principals could be table-sharing. |
For TPT it wouldn't be cycle, but multiple paths, which also fails. |
9497aae
to
3591dae
Compare
3591dae
to
62e8e3f
Compare
@AndriySvyryd New version up. |
var inverseSkipNavigation = skipNavigation.Inverse!; | ||
|
||
var deleteBehavior = DefaultDeleteBehavior(skipNavigation); | ||
var inverseDeleteBehavior = DefaultDeleteBehavior(inverseSkipNavigation); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably a corner case, but the inverse nav could already be configured as ClientCascade
explicitly, so we wouldn't need to do anything
62e8e3f
to
3c2e867
Compare
Fixes #28633